User-specified route rating and alerts

ABSTRACT

In some implementations, a user can provide ratings for routes, streets and/or locations. In some implementations, the user can initiate an alert associated with a location. In some implementations, user-specified ratings and alerts can be included in a route determination. In some implementations, route rating and alert information can be transmitted to other users and/or devices.

TECHNICAL FIELD

The disclosure generally relates to navigation and route selection.

BACKGROUND

Navigation systems are commonplace today. Users can access navigationsystems online, in cars and in mobile devices that can route a user fromone location to another. The routes selected by navigation systems aregenerally selected based on intrinsic qualities of a route, such asdistance, road type, and other features associated with the roads andstreets that make up the route.

SUMMARY

In some implementations, a user can provide ratings for routes, streetsand/or locations. In some implementations, the user can initiate analert associated with a location. In some implementations,user-specified ratings and alerts can be included in a routedetermination. In some implementations, route rating and alertinformation can be transmitted to other users and/or devices.

Particular implementations provide at least the following advantages:Route determination is improved by accounting for real-worldconsiderations and concerns of travelers. Real-time user-generatedalerts allow for faster and more accurate notification of events withinproximity of a user that might hinder the user's progress as the usertravels.

Details of one or more implementations are set forth in the accompanyingdrawings and the description below. Other features, aspects, andpotential advantages will be apparent from the description and drawings,and from the claims.

DESCRIPTION OF DRAWINGS

FIG. 1 illustrates an example navigation system for determining routesbased on user-specified route ratings and alerts.

FIG. 2 is an example graphical interface for receiving user inputspecifying route query parameters.

FIG. 3 illustrates an example graphical interface for presenting routesto a user.

FIG. 4 illustrates an example graphical interface for prompting a userfor a route rating.

FIG. 5 illustrates an example graphical interface for identifying alocation for rating.

FIG. 6 illustrates an example graphical interface for presentinginformation and invoking functions related to an identified location.

FIG. 7 illustrates an example graphical interface for receiving route orlocation rating information.

FIG. 8 is an example graphical interface for receiving user inputspecifying route query parameters, including desired routecharacteristics.

FIG. 9 is an example graphical interface for presenting routes that wereselected based on user-specified ratings, route characteristics andcomments.

FIG. 10 is an example graphical interface for presenting more ratinginformation associated with a route.

FIG. 11 is an example graphical interface for generating an alert.

FIG. 12 is an example graphical interface for presenting an alert.

FIG. 13 is flow diagram of an example route rating process.

FIG. 14 is flow diagram of an example location rating process.

FIG. 15 is a flow diagram of an example alert generation process.

FIG. 16 is a flow diagram of an example process for determining routesbased on user-specified rating and/or alert information.

FIG. 17 is a flow diagram of an example process for broadcastinguser-generated alerts.

FIG. 18 is a flow diagram of an example process for displaying routerating information on a mobile device.

FIG. 19 is a flow diagram of an example process for displaying alertinformation on a mobile device.

FIG. 20 is a block diagram of an example computing device that canimplement the features and processes of FIGS. 1-19.

Like reference symbols in the various drawings indicate like elements.

DETAILED DESCRIPTION Routing System Overview

FIG. 1 illustrates an example navigation system 100 for determiningroutes based on user-specified route ratings and alerts. System 100 caninclude mobile device 102, for example. Mobile device 102 can be acomputing device such as a laptop, smartphone, tablet computer or anyother device that can be configured for performing navigation functions.Mobile device 102 can include navigation engine 104 for performingnavigation functions on mobile device 102. For example, navigationengine 104 can be a software application that can be executed on mobiledevice 102. Navigation engine 104 can be configured to present a mapdisplay, present route information and receive user input related to thenavigation functions of mobile device 102, as described below.

In some implementations, navigation system 100 can include a navigationservice 106. For example, navigation service 106 can be a network (e.g.,Internet, World Wide Web) based service for providing route informationto mobile devices (e.g., mobile device 102). Navigation service 106 caninclude route engine 108. For example, route engine 108 can be anapplication or routine within navigation 106 for determining routesbased on route query parameters received from mobile device 102.Navigation engine 108 can determine routes based on information storedin alert database 112 and/or rating database 110, for example.

In some implementations, rating database 110 can store informationrelated to users' ratings of routes and/or locations. For example, auser of mobile device 102 can interact with navigation engine 104 toprovide ratings for routes and/or locations. The ratings informationprovided by the user can be transmitted to navigation service 106through network 114. Navigation service 106 can store the ratingsinformation in rating database 110 and route engine can determine routesbased on the ratings information stored in rating database 110.

In some implementations, alert database 112 can store informationrelated to user-initiated alerts. For example, if a user is travellingalong a road and notices an accident, the user can initiate an accidentalert by providing input to a graphical interface of navigation engine104 on mobile device 102. The alert information, including a locationassociated with the alert, can be transmitted to navigation service 106through network 114 and stored in alert database 112. In someimplementations, route engine 108 can determine routes based on thealert information stored in alert database 108.

In some implementations, alerts can be broadcast to mobile devices basedon the locations of the mobile devices. For example, navigation service106 can receive information identifying the current location of mobiledevice 102. If the current location of mobile device 102 is proximate toa location associated with the alert, the navigation service cantransmit the alert to mobile device 102 and mobile device 102 canpresent the alert (e.g., with a sound, graphical display, or both) tothe user of mobile device 102.

In some implementations, all of the alerts within an area proximate tomobile device 102 can be transmitted to the mobile device 102 and mobiledevice 102 can determine when to present the alerts to the user. Forexample, mobile device 102 can be configured to receive all alertinformation associated with locations within five miles of the currentlocation of mobile device 102. Once the alert information is received,mobile device 102 can determine when to present individual alerts to theuser based on the proximity of mobile device 102 to the locationassociated with the alert.

In some implementations, the alert information stored in alert database112 can be removed from alert database 112 after a period of time. Forexample, alerts are often associated with events (e.g., an accident, aprotest, etc.) that last only a short period of time. In someimplementations, when an alert is generated, the alert can be associatedwith a period of time (e.g., 20 minutes, 1 hour, etc.). After the periodof time has elapsed (e.g., the alert has expired), the alert can beremoved from alert database 112. Details of the implementationsdescribed herein are described further with reference to FIGS. 2-20below.

FIG. 2 is an example graphical interface 200 for receiving user inputspecifying route query parameters. For example, graphical interface 200can be a graphical interface of mobile device 102. Graphical interface200 can include an input field 202 for specifying a start location. Forexample, a user can use a virtual keyboard to provide input to inputfield 202 that specifies a starting address or location for a route.Graphical interface 200 can include an input field 204 for specifying anend location. For example, a user can user a virtual keyboard to provideinput to input field 204 that specifies an ending address or locationfor a route. In some implementations, the starting and ending addressesor locations can be selected from an address book application accessibleto mobile device 102. In some implementations, a user can selectgraphical element 208 to close graphical interface 200 of mobile device102.

In some implementations, once the starting and ending locations arespecified, a user can select graphical element 206 to have one or moreroutes generated between the starting location and the ending location.For example, the starting and ending locations can be transmitted tonavigation service 106 and route engine 108 can generate routes based onthe starting and ending locations. Once the routes are generated, theroutes can be transmitted to mobile device 102 and presented to theuser.

FIG. 3 illustrates an example graphical interface 300 for presentingroutes to a user. For example, graphical interface 300 can be agraphical interface of mobile device 102. In some implementations,graphical interface 300 can display a map that presents one or moreroutes to a user. For example, graphical interface 300 can displayroutes between start location 302 (point A) and end location 304 (pointB). The routes between start location 302 and end location 304 can beidentified by graphical elements 306, 308 and 310. In someimplementations, a user can select one of graphical elements 306, 308 or310 to display route information for the route associated with theselected graphical element. For example, route information (e.g., routeidentifier, route distance, estimated travel time, etc.) for theselected route can be displayed in information area 312. In someimplementations, the user can start navigating the selected route byselecting graphical element 314.

Prompting for a Route Rating

FIG. 4 illustrates an example graphical interface 400 for prompting auser for a route rating. For example, graphical interface 400 can be aninterface of mobile device 102. In some implementations, graphicalinterface 400 can present a map display that includes a portion of aroute. For example, graphical interface 400 can display a route segmentor the entire route. In some implementations, navigation engine 104 ofmobile device 102 can detect when mobile device 102 is approaching orhas reached the end location 402 (e.g., destination) associated with aselected route. For example, as mobile device 102 is navigating a routeselected in graphical interface 300, mobile device 102 can monitor thecurrent location 404 of mobile device 102. Mobile device 102 can beequipped with sensors (e.g., GPS receiver, accelerometer, magnetometer,wireless network adapters, etc.) that can be used to determine thecurrent location of mobile device 102, for example. Navigation engine104 can compare the current location 404 of mobile device 102 to endlocation 402 to determine when the mobile device has reached the end ofthe route.

In some implementations, a prompt for a route rating can be displayedwhen mobile device 102 has reached or approaches the end of a navigatedroute. For example, graphical interface 400 can display information area406 including an indication that mobile device 102 has reached the endof the route. Graphical interface 400 can display graphical element 408to give the user an opportunity to rate the route that mobile device 102just traveled. For example, graphical element 408 can be a button forinvoking graphical interface 700 of FIG. 7 for receiving route ratinginput from the user.

Rating a Location

FIG. 5 illustrates an example graphical interface 500 for identifying alocation for rating. For example, graphical interface 500 can be aninterface of mobile device 102. Graphical interface 500 can present mapdisplay 502. In some implementations, a user can provide input to mapdisplay 502 that identifies a location on map display 502. For example,a user can provide touch input to map display 502 to identify a locationon map display 502. The location can correspond to a street orintersection, for example. The location can be marked on map display 502by graphical element 504. For example, graphical element 504 can be apin that indicates the user-identified location. In someimplementations, graphical element 506 can be displayed in associationwith graphical element 504. For example, graphical element 506 canpresent information that describes or identifies the location associatedwith graphical element 504. Graphical element 506 can display a name ofa street or names of intersecting streets, for example. Graphicalelement 506 can be displayed in response to the user selecting graphicalelement 504. In some implementations, a user can select graphicalelement 506 to invoke a graphical interface 600 of FIG. 6.

FIG. 6 illustrates an example graphical interface 600 for presentinginformation and invoking functions related to an identified location.For example, graphical interface 600 can be an interface of mobiledevice 102. Graphical interface 600 can include graphical element 602for presenting information (e.g., an address, geographical coordinates,street intersection, etc.) that describes the identified location.Graphical interface 600 can include graphical element 604 for returningto the map display of graphical interface 500.

In some implementations, graphical interface 600 can include graphicalelement 606 for invoking an interface for generating an alert associatedwith the selected location. For example, selection of graphical element606 can cause graphical interface 1100 of FIG. 11 to be displayed.

In some implementations, graphical interface 600 can include graphicalelement 608 for invoking an interface for receiving location ratinginformation. For example, graphical element 608 can be a button forinvoking graphical interface 700 of FIG. 7 for receiving location ratinginput from the user.

Rating Interface

FIG. 7 illustrates an example graphical interface 700 for receivingroute or location rating information. For example, when graphicalinterface 700 is invoked from graphical interface 400, graphicalinterface 700 can be configured to receive route rating information.When graphical interface 700 is invoked from graphical interface 600,graphical interface 700 can be configured to receive location ratinginformation.

In some implementations, graphical interface 700 can receive a ratingfor a route or a location. For example, graphical interface 700 can beconfigured to receive a rating on a binary scale (e.g., like or dislike,good or bad, etc.). Graphical interface can be configured to receive arating based on a non-binary scale (e.g., scale of one to five stars,scale of one to ten). In some implementations, graphical interface 700can present graphical element 702 for receiving a rating for a route orlocation. For example, graphical element 702 can include objects (e.g.,stars) that are selectable by the user to indicate a rating for a routeor location. If five objects are presented in order from left to right,the user can select the left most object to give the route or locationthe lowest rating (e.g., one star). The user can select the right mostobject to give the route or location the highest rating (e.g., fivestars). The user can select objects in the middle to give the route orlocation a rating between one and five. In some implementations,graphical element 702 can present a pull-down menu, check boxes, or anyother type of graphical element suitable for indicating a rating value.

In some implementations, graphical interface 700 can include graphicalelement 704 for identifying characteristics of a route or location. Forexample, graphical element 704 can present pre-defined characteristicsthat are commonly associated with a route or location. For example, thecharacteristics can correspond to an amount of traffic, speed of travel,quality of road surfaces and/or facilities observed along the route orat the location. Other characteristics, such as events observed (e.g.,frequent accidents, construction, etc.), can be presented as well bygraphical element 704. In some implementations, a user can select one ormore characteristics to associate with the route or location. Forexample, a user can check checkboxes associated with characteristicsthat the user wants to associate with the route or location, asillustrated by FIG. 7. In some implementations, a user can selectcharacteristics from a pull-down menu or another type of graphicalinterface object.

In some implementations, a user can provide comments for a route orlocation. For example, if the user feels that the pre-defined set ofcharacteristics do not adequately describe the route or location, theuser can type text into comment field 706. In some implementations, whenthe user has finished providing route or location rating input tographical interface 700, the user can select graphical element 708 tosubmit the user's rating information for the route or location. Forexample, mobile device 102 can transmit the rating information (e.g.,rating value, selected characteristics, comments) for the route orlocation to navigation service 106 and navigation service 106 can storethe rating information in rating database 110.

Route Selection Based on User Ratings

FIG. 8 is an example graphical interface 800 for receiving user inputspecifying route query parameters, including desired routecharacteristics. In some implementations, a user can specify startingand ending locations (e.g., a destination) for a route, as describedabove with reference to FIG. 2. In some implementations, when specifyinga destination for a route, the user can specify one or morecharacteristics of the route. For example, if a user wants to travelfrom point A (starting location) to point B (ending location) along ascenic route, the user can specify “scenic route” in input field 204. Auser can specify any characteristic in input field 204. For example, auser can specify one or more of the pre-defined route or location ratingcharacteristics, described above with reference to FIG. 7. A user canspecify characteristics or terms that are not pre-definedcharacteristics. For example, characteristics and terms entered intoinput field 204 can be compared to ratings comments associated withroutes to determine routes that match the characteristics and terms.

In some implementations, a user can interact with graphical element 802to select one or more pre-defined characteristics from list 804. Forexample, graphical element 802 can be a pull-down menu which, whenselected, displays list 804. In some implementations, graphicalinterface 800 can present a graphical element that allows for selectionof pre-defined characteristics, such as the checkboxes described withreference to graphical element 704 of FIG. 7. For example, pre-definedcharacteristics can be presented in association with checkboxes forselecting the pre-defined characteristics.

In some implementations, graphical interface 800 can receive inputspecifying a minimum rating for a route. For example, if the ratingscale is a range between one and five stars, the user can specify thatthe route should have no less than a four star rating. In someimplementations, when a user selects graphical element 206 to initiate aroute determination, the route query parameters, including the routecharacteristics, terms and/or minimum rating, can be transmitted toroute engine 108 at navigation service 106 for determining routes thatmatch the route query parameters.

FIG. 9 is an example graphical interface 900 for presenting routes thatwere selected based on user-specified ratings, route characteristics andcomments. For example, route 1, route 2 and route 3 can be determined byroute engine 108 based on a comparison of route query parameters andrating information stored in rating database 110. For example, ratingdatabase 110 can store the route and/or location rating informationprovided by users as input to graphical interface 700 of FIG. 7.

In some implementations, a user can select graphical element 310 todisplay information associated with a route, as described above withreference to FIG. 3. If user-specified rating information is availablefor the selected route, information area 312 can display ratinginformation associated with the route. For example, information area 312can display an average of the user ratings 902 for the route and/or themost commonly selected pre-defined route characteristics 904 (e.g., thetop five most selected characteristics) associated with the route. Insome implementations, a user can select graphical element 906 to displayadditional route rating information. For example, graphical element 906can be a selectable text element (e.g., link, hyperlink, etc.) which,when selected, causes graphical interface 1000 of FIG. 10 to bedisplayed.

FIG. 10 is an example graphical interface 1000 for presenting additionalrating information associated with a route. In some implementations,when graphical element 906 is selected on graphical interface 900,information area 1002 can be displayed. For example, information area1002 can present the most frequently occurring comments received in userratings of the selected route. Information area 1002 can also presentadditional pre-defined route characteristics that were selected by usersfor the selected route.

User Initiated Alerts

FIG. 11 is an example graphical interface 1100 for generating an alert.For example, graphical interface 1100 can be presented in response to auser selecting graphical element 606 of FIG. 6. In some implementations,graphical interface 1100 can be presented in response to a userselecting graphical element 504 of FIG. 5. For example, if mobile device102 is configured to receive touch input, a user can provide sustainedtouch input (e.g., touch for 2 seconds) associated with graphicalelement 504 to cause graphical interface 1100 to appear. The geographiclocation associated with graphical element 504 can be used as thelocation of the alert.

In some implementations, graphical interface 1100 can be presented inresponse to touch input anywhere on map display 502 of FIG. 5. Forexample, a user and mobile device 102 traveling along a road may beforced to stop because a traffic accident is blocking the user'sprogress. The current location of the user and the current locationmobile device 102 will likely be proximate to the location of thetraffic accident. Because the location of mobile device 102 is proximateto the traffic accident, the current location of mobile device 102 canbe used to specify the location of accident and the location of thealert. For example, a sustained touch input (e.g., touch for 2 seconds)to map display 502 can cause graphical interface 1100 to be displayed.

In some implementations, graphical interface 1100 can include graphicalelements 1102-1110 for specifying a type of alert. For example, a usercan select graphical element 1102 (e.g., a button) to specify anaccident alert. In some implementations, graphical interface 1100 caninclude graphical element 1112 for specifying a duration of time duringwhich the alert will be active. For example, the user can specify thatthe alert should be active for the next forty-five minutes. Whenforty-five minutes has passed, navigation service 106 can remove thealert from alert database 112. Once the user has defined the type ofalert and duration of the alert, the user can select graphical element1114 to submit the alert to navigation service 106 of FIG. 1 and closegraphical interface 1100. For example, mobile device 102 can transmitthe alert information to navigation service 106. In someimplementations, navigation service 106 can add the alert information(e.g., location, alert type, and duration) to alert database 112.

FIG. 12 is an example graphical interface 1200 for presenting an alert.For example, graphical interface 1200 can be an interface for presentingalerts on mobile device 102. In some implementations, mobile device 102can transmit the current location of mobile device 102 to navigationservice 106. Navigation service 106 can compare the current location ofmobile device 102 to locations associated with alert information inalert database 112 to determine if any of there are any alerts proximateto mobile device 102. For example, navigation service 106 can determineif there are any alerts associated with locations within one mile of thecurrent location of mobile device 102. If navigation service 106determines that there are alerts proximate to the location of mobiledevice 102, navigation service 106 can transmit the alert information tomobile device 102.

In some implementations, alert information can be presented on graphicalinterface 1200. For example, graphical element 1202 can represent thecurrent location of mobile device 102. Graphical element 1204 (e.g., apin) can be displayed to identify the location associated with an alertreceived from navigation service 106. Graphical element 1206 can displayinformation identifying the type of alert. In some implementations, analert received at mobile device 102 can cause mobile device 102 togenerate a sound. For example, when mobile device 102 receives an alert,mobile device 102 can generate an alarm sound to notify the user of thereceived alert.

In some implementations, routes can be determined based on alertinformation. For example, a user can specify route query parameters ongraphical interface 800 of FIG. 8. Graphical interface 800 can receiveinput from the user specifying that locations associated with alertsshould be avoided when determining routes. When a user has specifiedthat alert locations should be avoided, route engine 108 can determineroutes between the start location and the end location and filter outroutes that include locations associated with the alerts stored in alertdatabase 112.

Example Processes

FIG. 13 is flow diagram of an example route rating process 1300. At step1302, a map and route are displayed. For example, a user of a mobiledevice can request a route from a starting location to an endinglocation (destination). The request can be transmitted to a navigationservice. The navigation service can transmit route information back tothe mobile device. The mobile device can display a map and the routeinformation received from the navigation service.

At step 1304, the mobile device can determine when the mobile devicereaches the destination. For example, the mobile device can beconfigured with GPS or another location technology from which thecurrent location of the mobile device can be obtained. The mobile devicecan compare the mobile device's current location to the destinationlocation of the route to determine when the mobile device has reachedthe destination.

At step 1306, the user of the mobile device is prompted for a routerating when the mobile device has reached the destination. For example,a graphical interface of the mobile device can present informationindicating that the destination has been reached and allow the user toselect to provide a route rating, as described with reference to FIG. 4.

At step 1308, a rating interface can be displayed. For example,graphical interface 700 of FIG. 7 can be displayed. At step 1310, routerating information can be received. For example, the user can provide aroute rating, including route characteristics and comments, as describedwith reference to FIG. 7.

At step 1312, the route rating information can be uploaded to thenavigation service. For example, mobile device 102 can transmit theroute rating information to navigation service 106. Navigation service106 can store the route rating information in rating database 110 andreference the route rating information when determining routes in thefuture.

FIG. 14 is flow diagram of an example location rating process 1400. Atstep 1402, a map is displayed. For example, a map display can bepresented on graphical interface 500 of mobile device 102. At step 1404,an identification of a location on the map is received. For example, auser can provide input corresponding to a location on the map displayedon graphical interface 500.

At step 1406, a location rating can be received. For example, the usercan input information rating the identified location, as described withreference to FIGS. 5-7. At step 1408, the location rating can beuploaded to the navigation service. For example, mobile device 102 cantransmit the location rating information to navigation service 106.Navigation service 106 can store the location rating information inrating database 110 and reference the location rating information whendetermining routes in the future.

FIG. 15 is a flow diagram of an example alert generation process 1500.At step 1502, a map is displayed. For example, a map display can bepresented on mobile device 102. At step 1504, identification of a maplocation is received. For example, a user can provide input to identifya location on the map display or the location can be derived from thecurrent location of the mobile device.

At step 1506, alert information for the identified location is received.For example, a user can input information describing or defining analert as described with reference to FIG. 11. At step 1508, the alertinformation, including alert location, can be uploaded to a navigationservice. For example, mobile device 102 can transmit the alertinformation to navigation service 106. Navigation service 106 can storethe alert information in alert database 112 and reference the alertinformation when determining routes in the future or when a currentlocation of the mobile device is received at navigation service 106.

FIG. 16 is a flow diagram of an example process 1600 for determiningroutes based on user-specified rating and/or alert information. At step1602, rating and/or alert information is received from a mobile device.For example, mobile device 102 can transmit route and/or location ratinginformation to navigation service 106. Route and location ratinginformation can include the rating information described with referenceto FIG. 7, for example. Mobile device 102 can transmit alert informationto navigation service 106. Alert information can include the alertinformation described with reference to FIG. 11, for example.

At step 1604, rating and/or alert information is stored. For example,navigation service 106 can store route and location rating informationin rating database 110. Navigation service 106 can store alertinformation in alert database 112.

At step 1606, rating and/or alert information is aggregated. Forexample, rating information received for a route from multiple devicesand/or user can be combined into an aggregate rating. Rating values canbe averaged. Route characteristics can be counted and associated with afrequency value (e.g., frequency of occurrence). Comments can beanalyzed, summarized, categorized and/or counted to determine the mostfrequently received comments.

In some implementations, alert information can be aggregated. Forexample, if navigation service 106 received multiple accident alerts fora single location (or proximate to a single location), those alerts canbe combined into a single accident alert. If the alerts are associatedwith different locations that are geographically proximate, thelocations of the alert can be averaged and the averaged location can beassigned as the location associated with the aggregated alerts.

At step 1608, a route query is received from a mobile device. Forexample, a route query can be received from mobile device 102 atnavigation service 106. The route query can include route parameters, asdescribed with reference to FIG. 8 above.

At step 1610, routes are generated based on the route query and ratingand alert information. For example, route engine 108 can determineroutes between a starting location (point A) and an ending location(point B), as specified by the user in the route parameters of the routequery. For example, route engine 108 can determine the five routesbetween point A and point B that have the shortest distance or theshortest travel time.

In some implementations, route engine 108 can filter or prioritize thedetermined routes based on rating information. For example, if routeand/or location rating information exist in rating database 110 for thedetermined routes (or portions of the determined routes, or locationsalong the determined routes), route engine 108 can filter or prioritizethe determined routes based on the rating information. If, for example,the user's query indicates that the user wants a “scenic” route and theroute ratings associated with one of the determined routes indicatesthat the route is a scenic route, then the route associated with the“scenic” characteristic will be prioritized or presented before theother determined routes. If the user's query indicates that the userwants to avoid construction, routes that are associated with aconstruction characteristic can be filtered out or removed from the setof determined routes. If the user's query indicates that a four-starrating is required, then routes with less than a four star rating can beremoved from the set of determined routes.

In some implementations, route engine 108 can filter or prioritize thedetermined routes based on alert information. For example, route engine108 can determine if any of the alerts stored in alert database 112 areassociated with locations along any of the determined routes. If a routeincludes a location associated with an alert (e.g., accident alert), theroute can be reduced in priority (e.g., presented last, or moved to theend of the list of routes) or filtered from the set of determinedroutes.

At step 1612, routes, ratings and/or alert information is transmitted tothe mobile device. For example, once route engine 108 determines theroutes between point A and point B that satisfy the route query,navigation service 106 can transmit the determined, prioritized and/orfiltered routes to mobile device 102 for presentation to the user.Navigation service 106 can also transmit ratings and alert informationassociated with each route to mobile device 102 for presentation to theuser.

FIG. 17 is a flow diagram of an example process 1700 for broadcastinguser-generated alerts. At step 1702, alert information is received. Forexample, alert information (e.g., alert type, duration or time period ofthe alert, and location associated with the alert) can be received atnavigation service 106. The transmitted alert information can include aproximity value for receiving alerts. For example, the proximity valuecan be a user-specified distance value that can be used to determinewhich alert information to transmit to mobile device 102.

At step 1704, the alert information can be stored. For example,navigation service 106 can store the received alert information in alertdatabase 112. Navigation service 106 and/or route engine 108 can managealert database 112. For example, alert database 112 can be managed suchthat expired alerts are removed from alert database 112. An expiredalert can be an alert that has been in database 112 for a period of timeexceeding the duration or period of time assigned to the alert by theuser, for example.

At step 1706, the current location of a mobile device can be received.For example, mobile device 102 can transmit the current location ofmobile device 102 to navigation service 106. Navigation service 106 cancompare the current location of mobile device 102 to locationsassociated with alerts in alert database 112 to identify which alertinformation is within the specified proximity (e.g., within theuser-specified distance) of mobile device 102.

At step 1708, alert information can be transmitted to the mobile device.For example, navigation service 106 can transmit the alert informationidentified at step 1706 to mobile device 102.

In some implementations, alert information can be identified based on aroute associated with the mobile device. For example, if mobile device102 has previously requested a route from navigation service 106,navigation service 106 can identify alerts that are associated withlocations along the route and transmit those alerts to mobile device102. Mobile device 102 can then display the alerts along the route andgive the user an opportunity to change route and/or avoid those alertlocations.

For example, when a user selects or starts a route on mobile device 102,mobile device 102 can transmit information identifying the route (activeroute) and an identifier of the mobile device to navigation service 106.Navigation service 106 can store the mobile device identifier inassociation with the active route information in an active routedatabase. When navigation service 106 receives new alert information,the location associated with the new alert information can be comparedto locations along active routes and, if the new alert information islocated along an active route, navigation service 106 can transmit thenew alert information to mobile devices traveling along the activeroute. A mobile device can be disassociated from an active route oncethe mobile device reaches the route destination. For example, mobiledevice 102 can transmit a message to navigation service 106 indicatingthat mobile device 102 has reached the route destination. Navigationservice 106 can remove the active route information and/or mobile deviceidentifier from the active route database.

FIG. 18 is a flow diagram of an example process 1800 for displayingroute rating information on a mobile device. At step 1802, a route querycan be submitted. For example, a user can provide input to graphicalinterface 800 (FIG. 8) of mobile device 102. Mobile device 102 cantransmit the route query, including route parameters, to navigationservice 106.

At step 1804, route and/or location rating information can be received.For example, when navigation service 106 responds to the route query bygenerating a route and transmitting the route to mobile device 102,navigation service 106 can also transmit route rating information forthe route and/or location rating information for locations along theroute. In some implementations, when route or location ratings have beenreceived from many users, the ratings information can be aggregated andonly the most frequently seen (e.g., top 5 most frequently receivedcharacteristics, average ratings values, etc.) ratings information willbe received at mobile device 102.

At step 1806, the rating information can be displayed. For example, thereceived ratings information can be displayed on graphical interface 900of FIG. 9 or graphical interface 1000 of FIG. 10.

FIG. 19 is a flow diagram of an example process 1900 for displayingalert information on a mobile device. At step 1908, the current locationof a mobile device can be submitted. For example, mobile device 102 cantransmit the current location of mobile device 102 to navigation service106.

At step 1910, alert information can be received. For example, mobiledevice 102 can receive alert information from navigation service 106. Atstep 1912, alert information can be presented on the mobile device. Forexample, alert information can be presented on graphical interface 1200of FIG. 12

Example System Architecture

FIG. 20 is a block diagram of an example computing device 2000 that canimplement the features and processes of FIGS. 1-19. For example,computing device 2000 can correspond to mobile device 102 of FIG. 1. Thecomputing device 2000 can include a memory interface 2002, one or moredata processors, image processors and/or central processing units 2004,and a peripherals interface 2006. The memory interface 2002, the one ormore processors 2004 and/or the peripherals interface 2006 can beseparate components or can be integrated in one or more integratedcircuits. The various components in the computing device 2000 can becoupled by one or more communication buses or signal lines.

Sensors, devices, and subsystems can be coupled to the peripheralsinterface 2006 to facilitate multiple functionalities. For example, amotion sensor 2010, a light sensor 2012, and a proximity sensor 2014 canbe coupled to the peripherals interface 2006 to facilitate orientation,lighting, and proximity functions. Other sensors 2016 can also beconnected to the peripherals interface 2006, such as a global navigationsatellite system (GNSS) (e.g., GPS receiver), a temperature sensor, abiometric sensor, or other sensing device, to facilitate relatedfunctionalities.

A camera subsystem 2020 and an optical sensor 2022, e.g., a chargedcoupled device (CCD) or a complementary metal-oxide semiconductor (CMOS)optical sensor, can be utilized to facilitate camera functions, such asrecording photographs and video clips. The camera subsystem 2020 and theoptical sensor 2022 can be used to collect images of a user to be usedduring authentication of a user, e.g., by performing facial recognitionanalysis.

Communication functions can be facilitated through one or more wirelesscommunication subsystems 2024, which can include radio frequencyreceivers and transmitters and/or optical (e.g., infrared) receivers andtransmitters. The specific design and implementation of thecommunication subsystem 2024 can depend on the communication network(s)over which the computing device 2000 is intended to operate. Forexample, the computing device 2000 can include communication subsystems2024 designed to operate over a GSM network, a GPRS network, an EDGEnetwork, a Wi-Fi or WiMax network, and a Bluetooth™ network. Inparticular, the wireless communication subsystems 2024 can includehosting protocols such that the device 100 can be configured as a basestation for other wireless devices.

An audio subsystem 2026 can be coupled to a speaker 2028 and amicrophone 2030 to facilitate voice-enabled functions, such as speakerrecognition, voice replication, digital recording, and telephonyfunctions. The audio subsystem 2026 can be configured to facilitatepresenting location alert sounds, as described above with reference toFIGS. 1-19.

The I/O subsystem 2040 can include a touch-surface controller 2042and/or other input controller(s) 2044. The touch-surface controller 2042can be coupled to a touch surface 2046. The touch surface 2046 andtouch-surface controller 2042 can, for example, detect contact andmovement or break thereof using any of a plurality of touch sensitivitytechnologies, including but not limited to capacitive, resistive,infrared, and surface acoustic wave technologies, as well as otherproximity sensor arrays or other elements for determining one or morepoints of contact with the touch surface 2046.

The other input controller(s) 2044 can be coupled to other input/controldevices 2048, such as one or more buttons, rocker switches, thumb-wheel,infrared port, USB port, and/or a pointer device such as a stylus. Theone or more buttons (not shown) can include an up/down button for volumecontrol of the speaker 2028 and/or the microphone 2030.

In one implementation, a pressing of the button for a first duration candisengage a lock of the touch surface 2046; and a pressing of the buttonfor a second duration that is longer than the first duration can turnpower to the computing device 2000 on or off. Pressing the button for athird duration can activate a voice control, or voice command, modulethat enables the user to speak commands into the microphone 2030 tocause the device to execute the spoken command. The user can customize afunctionality of one or more of the buttons. The touch surface 2046 can,for example, also be used to implement virtual or soft buttons and/or akeyboard.

In some implementations, the computing device 2000 can present recordedaudio and/or video files, such as MP3, AAC, and MPEG files. In someimplementations, the computing device 2000 can include the functionalityof an MP3 player, such as an iPod™. The computing device 2000 can,therefore, include a 36-pin connector that is compatible with the iPod.Other input/output and control devices can also be used.

The memory interface 2002 can be coupled to memory 2050. The memory 2050can include high-speed random access memory and/or non-volatile memory,such as one or more magnetic disk storage devices, one or more opticalstorage devices, and/or flash memory (e.g., NAND, NOR). The memory 2050can store an operating system 2052, such as Darwin, RTXC, LINUX, UNIX,OS X, WINDOWS, or an embedded operating system such as VxWorks.

The operating system 2052 can include instructions for handling basicsystem services and for performing hardware dependent tasks. In someimplementations, the operating system 2052 can be a kernel (e.g., UNIXkernel). In some implementations, the operating system 2052 can includeinstructions for performing voice authentication. For example, operatingsystem 2052 can implement the route rating and alert features asdescribed with reference to FIGS. 1-19.

The memory 2050 can also store communication instructions 2054 tofacilitate communicating with one or more additional devices, one ormore computers and/or one or more servers. The memory 2050 can includegraphical user interface instructions 2056 to facilitate graphic userinterface processing; sensor processing instructions 2058 to facilitatesensor-related processing and functions; phone instructions 2060 tofacilitate phone-related processes and functions; electronic messaginginstructions 2062 to facilitate electronic-messaging related processesand functions; web browsing instructions 2064 to facilitate webbrowsing-related processes and functions; media processing instructions2066 to facilitate media processing-related processes and functions;GNSS/Navigation instructions 2068 to facilitate GNSS andnavigation-related processes and instructions; and/or camerainstructions 2070 to facilitate camera-related processes and functions.

The memory 2050 can store route rating and alert software instructions2072 to facilitate other processes and functions, such as the routerating and alert processes and functions as described with reference toFIGS. 1-19. The memory 2050 can also store other software instructions(not shown), such as web video instructions to facilitate webvideo-related processes and functions; and/or web shopping instructionsto facilitate web shopping-related processes and functions. In someimplementations, the media processing instructions 2066 are divided intoaudio processing instructions and video processing instructions tofacilitate audio processing-related processes and functions and videoprocessing-related processes and functions, respectively. An activationrecord and International Mobile Equipment Identity (IMEI) 2074 orsimilar hardware identifier can also be stored in memory 2050.

Each of the above identified instructions and applications cancorrespond to a set of instructions for performing one or more functionsdescribed above. These instructions need not be implemented as separatesoftware programs, procedures, or modules. The memory 2050 can includeadditional instructions or fewer instructions. Furthermore, variousfunctions of the computing device 2000 can be implemented in hardwareand/or in software, including in one or more signal processing and/orapplication specific integrated circuits.

What is claimed is:
 1. A method comprising: presenting a map display and a route on a mobile device; monitoring a current location of the mobile device as the mobile device moves along the route; determining that the current location of the mobile device corresponds to a location near the end of the route; in response to the determination, displaying a prompt for input rating the route; and receiving user input comprising rating information for the route.
 2. The method of claim 1, wherein the input comprises a selection of a binary rating.
 3. The method of claim 1, wherein the input comprises a selection of a value on a rating scale.
 4. The method of claim 1, wherein the input comprises a selection of one or more characteristics to associate with the route.
 5. The method of claim 1, wherein the input comprises textual input describing the route.
 6. The method of claim 1, further comprising: transmitting the rating information to a navigation service, where the navigation service generates routes based on user-specified rating information.
 7. The method of claim 1, further comprising: receiving route information describing the route, where the route information was generated by a navigation service that generates routes based on user-specified rating information.
 8. A non-transitory computer-readable medium including one or more sequences of instructions which, when executed by one or more processors, causes: presenting a map display and a route on a mobile device; monitoring a current location of the mobile device as the mobile device moves along the route; determining that the current location of the mobile device corresponds to a location near the end of the route; in response to the determination, displaying a prompt for input rating the route; and receiving user input comprising rating information for the route.
 9. The computer-readable medium of claim 8, wherein the input comprises a selection of a binary rating.
 10. The computer-readable medium of claim 8, wherein the input comprises a selection of a value on a rating scale.
 11. The computer-readable medium of claim 8, wherein the input comprises a selection of one or more characteristics to associate with the route.
 12. The computer-readable medium of claim 8, wherein the input comprises textual input describing the route.
 13. The computer-readable medium of claim 8, wherein the instructions cause: transmitting the rating information to a navigation service, where the navigation service generates routes based on user-specified rating information.
 14. The computer-readable medium of claim 8, wherein the instructions cause: receiving route information describing the route, where the route information was generated by a navigation service that generates routes based on user-specified rating information.
 15. A system comprising: one or more processors; and a computer-readable medium including one or more sequences of instructions which, when executed by the one or more processors, causes: presenting a map display and a route on the system; monitoring a current location of the system as the system moves along the route; determining that the current location of the system corresponds to a location the end of the route; in response to the determination, displaying a prompt for input rating the route; and receiving user input comprising rating information for the route.
 16. The system of claim 15, wherein the input comprises a selection of a binary rating.
 17. The system of claim 15, wherein the input comprises a selection of a value on a rating scale.
 18. The system of claim 15, wherein the input comprises a selection of one or more characteristics to associate with the route.
 19. The system of claim 15, wherein the input comprises textual input describing the route.
 20. The system of claim 15, wherein the instructions cause: transmitting the rating information to a navigation service, where the navigation service generates routes based on user-specified rating information.
 21. The system of claim 15, wherein the instructions cause: receiving route information describing the route, where the route information was generated by a navigation service that generates routes based on user-specified rating information. 